xtensa-build-zephyr: use separate Zephyr config for TGPH builds#5443
Conversation
Zephyr recently added support for separate configs for 2-core and 4-core variants of cAVS2.5. Use the new "tgph" configuration for when building SOF for TigerLake-H variant. BugLink: thesofproject#5018 Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
|
@kv2019i @keqiaozhang do we need to update CI Zephyr commit ID ? |
|
Yes @lgirdwood , we need SOF CI to pick latest Zephyr upstream before this can be tested and merged. |
|
We have two xtensa-build-zephyr build scripts right now, transitioning from .sh to .py. Please keep the filename extension in the commit subject otherwise it makes managing the transition period much harder than it has to be. |
|
@marc-hb wrote:
Ack. I'm updating both, so kept the title on purpose for both. |
|
SOFCI TEST |
Apologies I hastily copied this comment from another, similar PR that was updating only one of them. |
|
CI runtime failure is unrelated. |
Zephyr recently added support for separate configs for 2-core and 4-core
variants of cAVS2.5. Use the new "tgph" configuration for when building
SOF for TigerLake-H variant.
BugLink: #5018
Signed-off-by: Kai Vehmanen kai.vehmanen@linux.intel.com